Methods and systems for virtualization of storage services in an integrated chassis

ABSTRACT

In accordance with embodiments of the present disclosure, a system may include a chassis, one or more chassis management controllers housed in the chassis, and a switch management controller. The chassis may be configured to receive a plurality of modular information handling systems. The one or more chassis management controllers may be configured to receive a storage management command, encapsulate the storage management command in a first datagram, and communicate the first datagram to a switch management controller housed in the chassis. The switch management controller may be configured to extract the storage management command from the first datagram, identify a storage controller associated with the storage management command, and communicate an input/output control request to the storage controller based on the storage management command.

TECHNICAL FIELD

The present disclosure relates in general to information handlingsystems, and more particularly to virtualization of storage services inan integrated chassis.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Existing server architectures either provide a single monolithic servercapable of running one operating system and input/output (I/O) resourcesat a time, or bulky blade server chassis providing multiple servers andI/O control modules in a single chassis. A system chassis with multipleinformation handling systems with various peripheral and input/outputcapabilities common to the chassis as a whole may provide advantages, asit allows a blade server chassis in a small form factor, therebyproviding a blade server chassis with a size comparable to the size of amonolithic server. Implementation of a system chassis with multipleinformation handling systems with various peripheral and input/outputcapabilities common to the chassis as a whole presents numerouschallenges.

SUMMARY

In accordance with the teachings of the present disclosure, thedisadvantages and problems associated with virtualizing storage servicesin an integrated chassis have been reduced or eliminated.

In accordance with embodiments of the present disclosure, a system mayinclude a chassis, one or more chassis management controllers housed inthe chassis, and a switch management controller. The chassis may beconfigured to receive a plurality of modular information handlingsystems. The one or more chassis management controllers may beconfigured to receive a storage management command, encapsulate thestorage management command in a first datagram, and communicate thefirst datagram to a switch management controller housed in the chassis.The switch management controller may be configured to extract thestorage management command from the first datagram, identify a storagecontroller associated with the storage management command, andcommunicate an input/output control request to the storage controllerbased on the storage management command.

In accordance with these and other embodiments of the presentdisclosure, a method may include receiving a storage management commandat a chassis management controller housed in a chassis configured toreceive a plurality of modular information handling systems,encapsulating the storage management command in a first datagram,communicating the first datagram from the chassis management controllerto a switch management controller housed in the chassis, extracting thestorage management command from the first datagram, identifying astorage controller associated with the storage management command, andcommunicating an input/output control request from the switch managementcontroller to the storage controller based on the storage managementcommand.

Technical advantages of the present disclosure will be apparent to thoseof ordinary skill in the art in view of the following specification,claims, and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present embodiments and advantagesthereof may be acquired by referring to the following description takenin conjunction with the accompanying drawings, in which like referencenumbers indicate like features, and wherein:

FIG. 1 illustrates a block diagram of an example system chassis withmultiple information handling systems and with various peripheral andinput/output capabilities common to the chassis as a whole, inaccordance with certain embodiments of the present disclosure; and

FIG. 2 illustrates a flow chart of an example method for virtualizationof storage services in an intergrated chassis, in accordance withcertain embodiments of the present disclosure.

DETAILED DESCRIPTION

Preferred embodiments and their advantages are best understood byreference to FIGS. 1 and 2, wherein like numbers are used to indicatelike and corresponding parts.

For the purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system may be a personal computer, a PDA, aconsumer electronic device, a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include memory, one ormore processing resources such as a central processing unit (CPU) orhardware or software control logic. Additional components or theinformation handling system may include one or more storage devices, oneor more communications ports for communicating with external devices aswell as various input and output (I/O) devices, such as a keyboard, amouse, and a video display. The information handling system may alsoinclude one or more buses operable to transmit communication between thevarious hardware components.

For the purposes of this disclosure, information handling resources maybroadly refer to any component system, device or apparatus of aninformation handling system, including without limitation processors,busses, memories, input-output devices and/or interfaces, storageresources, network interfaces, motherboards, electromechanical devices(e.g., fans), displays, and power supplies.

For the purposes of this disclosure, computer-readable media may includeany instrumentality or aggregation of instrumentalities that may retaindata and/or instructions for a period of time. Computer-readable mediamay include, without limitation, storage media such as a direct accessstorage device (e.g., a hard disk drive or floppy disk), a sequentialaccess storage device (e.g., a tape disk drive), compact disk, CD-ROM,DVD, random access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), and/or flash memory; aswell as communications media such wires, optical fibers, microwaves,radio waves, and other electromagnetic and/or optical carriers; and/orany combination of the foregoing.

Information handling systems often use an array of physical storageresources (e.g., disk drives), such as a Redundant Array of IndependentDisks (RAID), for example, for storing information. Arrays of physicalstorage resources typically utilize multiple disks to perform input andoutput operations and can be structured to provide redundancy which mayincrease fault tolerance. Other advantages of arrays of physical storageresources may be increased data integrity, throughput and/or capacity.In operation, one or more physical storage resources disposed in anarray of physical storage resources may appear to an operating system asa single logical storage unit or “logical unit.” Implementations ofphysical storage resource arrays can range from a few physical storageresources disposed in a chassis, to hundreds of physical storageresources disposed in one or more separate storage enclosures.

FIG. 1 illustrates a block diagram of an example system 100 having achassis 101 with multiple information handling systems 102 and withvarious peripheral and input/output capabilities common to chassis 101as a whole, in accordance with certain embodiments of the presentdisclosure. As depicted in FIG. 1, system 100 may comprise a chassis 101including a plurality of information handling systems 102, a mid-plane106, one or more switches 110, a switch management controller 111, oneor more chassis management controller 112, a network interface 116, oneor more slots 120, one or more cables 124, one or more storageinterfaces 126, a disk drive backplane 128, a plurality of disk drives130, an optical media drive 132, a keyboard-video-mouse (KVM) interface134, and a user interface 136.

An information handling system 102 may generally be operable to receivedata from and/or communicate data to one or more disk drives 130 and/orother information handling resources of chassis 101 via mid-plane 106.In certain embodiments, an information handling system 102 may be aserver. In such embodiments, an information handling system may comprisea blade server having modular physical design. In these and otherembodiments, an information handling system 102 may comprise an M classserver. As depicted in FIG. 1, an information handling system 102 mayinclude a processor 103 and one or more switch interfaces 104communicatively coupled to the processor 103.

A processor 103 may include any system, device, or apparatus configuredto interpret and/or execute program instructions and/or process data,and may include, without limitation a microprocessor, microcontroller,digital signal processor (DSP), application specific integrated circuit(ASIC), or any other digital or analog circuitry configured to interpretand/or execute program instructions and/or process data. In someembodiments, processor 103 may interpret and/or execute programinstructions and/or process data stored in a memory, a hard drive 130,and/or another component of system 100.

A switch interface 104 may comprise any system, device, or apparatusconfigured to provide an interface between its associated informationhandling system 102 and switches 110. In some embodiments, switches 110may comprise Peripheral Component Interconnect Express (PCIe) switches,in which case a switch interface 104 may comprise a mezzanine cardconfigured to create a PCIe-compliant interface between its associatedinformation handling system 102 and switches 110. In other embodiments,a switch interface 104 may comprise an interposer. Use of switchinterfaces 104 in information handling systems 102 may allow for minimalchanges to be made to traditional servers (e.g., M class servers) whilesupporting the overall system architecture disclosed herein. AlthoughFIG. 1 depicts an implementation including a single switch interface 104per information handling system 102, in some embodiments eachinformation handling system 102 may include a plurality of switchinterfaces 102 for redundancy, high availability, and/or other reasons.

Mid-plane 106 may comprise any system, device, or apparatus configuredto interconnect modular information handling systems 102 withinformation handling resources of chassis 101. Accordingly, mid-plane106 may include slots and/or connectors configured to receiveinformation handling systems 102, switches 110, switch managementcontroller 111, chassis management controllers 112, storage controllers114, network interface 116, optical media drive 132, KVM interface 134,user interface 136, and/or other information handling resources. In oneembodiment, mid-plane 106 may include a single board configured tointerconnect modular information handling systems 102 with informationhandling resources. In another embodiment, mid-plane 106 may includemultiple boards configured to interconnect modular information handlingsystems 102 with information handling resources. In yet anotherembodiment, mid-plane 106 may include cabling configured to interconnectmodular information handling systems 102 with information handlingresources.

A switch 110 may comprise any system, device, or apparatus configured tocouple information handling systems 102 to storage controllers 114(e.g., via mid-plane 106) and slots 120 and perform switching betweeninformation handling systems 102 and various information handlingresources of system 100, including storage controllers 114 and slots120. In certain embodiments, a switch 110 may comprise a PCIe switch. Inother embodiments, a switch may comprise a generalized PC bus switch, anInfiniband switch, or other suitable switch. As shown in FIG. 1, chassis101 may include a plurality of switches 110. In such embodiments,switches 110 may operate in a redundant mode for shared devices (e.g.,storage controllers 114 and/or devices coupled to slots 120) and innon-redundant mode for non-shared/zoned devices. As used herein, shareddevices may refer to those which may be visible to more than oneinformation handling system 102, while non-shared devices may refer tothose which are visible to only a single information handling system102.

A chassis management controller 112 may be any system, device, orapparatus configured to facilitate management and/or control of system100, its information handling systems 102, and/or one or more of itscomponent its component information handling resources. A chassismanagement controller 102 may be configured to issue commands and/orother signals to manage and/or control information handling system 102and/or information handling resources of system 100. A chassismanagement controller 112 may comprise a microprocessor,microcontroller, digital signal processor (DSP), application specificintegrated circuit (ASIC), field programmable gate array (FPGA),erasable programmable read-only memory (EPROM), or any combinationthereof. As shown in FIG. 1, a chassis management controller 112 may becoupled to mid-plane 106. Also as shown in FIG. 1, system 100 mayinclude a plurality of chassis management controllers 112, and in suchembodiments, chassis management controllers 112 may be configured asredundant. In some embodiments, a chassis management controller 112 mayprovide a user interface and high level controls for management ofswitches 110, including configuring assignments of individualinformation handling systems 102 to non-shared information handlingresources of system 100. In these and other embodiments, a chassismanagement controller may define configurations of the storage subsystem(e.g., storage controllers 114, storage interfaces 126, disk drives 130,etc.) of system 100. For example, a chassis management controller mayprovide physical function configuration and status information thatwould normally occur at the driver level in traditional serverimplementations. Examples of physical functions include disk drivediscovery and status, RAID configuration and logical volume mapping.

In addition or alternatively, a chassis management controller 112 mayalso provide a management console for user/administrator access to thesefunctions. For example, a chassis management controller 112 mayimplement Intelligent Platform Management Interface (IPMI) or anothersuitable management protocol permitting a user to remotely access achassis management controller 112 to configure system 100 and itsvarious information handling resources. In such embodiments, a chassismanagement controller 112 may interface with a network interfaceseparate from network interface 116, thus allowing for “out-of-band”control of 100, such that communications to and from chassis managementcontroller 112 are communicated via a management channel physicallyisolated from an “in band” communication channel with network interface116. Thus, for example, if a failure occurs in system 100 that preventsan administrator from interfacing with system 100 via network interface116 and/or user interface 136 (e.g., operating system failure, powerfailure, etc.), the administrator may still be able to monitor and/ormanage system 100 (e.g., to diagnose problems that may have causedfailure) via a chassis management controller 112. In the same oralternative embodiments, chassis management controller 112 may allow anadministrator to remotely manage one or parameters associated withoperation of system 100 and its various information handling resources(e.g., power usage, processor allocation, memory allocation, securityprivileges, etc.). Although FIG. 1 depicts chassis as having two chassismanagement controllers 112, chassis 101 may include any suitable numberchassis management controllers 112.

A storage controller 114 may and include any system, apparatus, ordevice operable to manage the communication of data between one or moreof information handling systems 102 and one or more of disk drives 130.In certain embodiments, a storage controller 114 may providefunctionality including, without limitation, disk aggregation andredundancy (e.g., RAID), input/output (I/O) routing, and error detectionand recovery. As shown in FIG. 1, a storage controller 114 may coupledto a connector on mid-plane 106. Also as shown in FIG. 1, system 100 mayinclude a plurality of storage controllers 114, and in such embodiments,storage controllers 114 may be configured as redundant. In addition orin the alternative, storage controllers 114 may in some embodiments beshared among two or more information handling systems 102. As also shownin FIG. 1, each storage controller 114 may be coupled to one or morestorage interfaces 126 via cables 124. For example, in some embodiments,each storage controller 114 may be coupled to a single associatedstorage interface 126 via a cable 124. In other embodiments, eachstorage controller 114 may be coupled to two or more storage interfaces126 via a plurality of cables 124, thus permitting redundancy as shownin FIG. 1. Storage controllers 114 may also have features supportingshared storage and high availability. For example, in PCIeimplementations, a unique PCIe identifier may be used to indicate sharedstorage capability and compatibility in system 100.

In embodiments in which switches 110 comprise PCIe switches or switchesconfigured in accordance with another communication standard, chassismanagement controllers 112 may not be able to communicate directly withswitches 110. Available chassis management controllers 112 may not beconfigured in accordance with PCIe or other communication standardsavailable in switches 110, and it may not be desirable to create aproprietary chassis management controller 112 configured in accordancewith PCIe or such other communication standards for use in system 100due to cost concerns. Accordingly, challenges may exist in enablingmanagement functionality of storage devices (e.g., disk drives 130) viachassis management controllers 112 as direct PCIe communications (orcommunications via another communication protocol) may not be availablebetween

Accordingly, a switch management controller 111 may be communicativelyinterfaced between chassis management controllers 112 and switches 110,and configured to virtualize management communications between chassismanagement controllers 112 and switches 110 related to management ofstorage components (e.g., storage controllers 114, disk drives 130)and/or other components of system 100. Switch management controller 111may, in some embodiments, interface with switches 110 via a privatenetwork (e.g., an Ethernet network) internal to chassis 101. In suchembodiments, each switch 110 and switch management controller 111 mayestablish a Transmission Control Protocol/Internet Protocol (TCP/IP)socket for communication. In these and other embodiments, switchmanagement controller 111 may comprise a power PC management processoror processor similar in structure and/or function.

In operation, a chassis management controller 112 may receive a storagemanagement command (e.g., a storage application programming interface(API) call) from a management console or other interface. Chassismanagement controller 112 may encapsulate such command in a networkdatagram (e.g., an Ethernet packet, frame, or other datagram) andcommunicate such datagram via the private network to switch managementcontroller 111. Switch management controller 111 may receive suchdatagram and extract the command from the datagram. Based on analysis ofthe command, storage management controller 111 may identify a storagecontroller 114 associated with the command and execute an input/outputcontrol request to such storage controller 114 via an appropriate switch110. The storage controller 114 may communicate a reply (e.g., a returncode) via an appropriate switch to storage management controller 111,which reply storage management controller 111 may encapsulate into anetwork datagram (e.g., an Ethernet packet, frame, or other datagram)and communicate such datagram via the private network to a chassismanagement controller 112. The chassis management controller 112 mayextract the reply from the datagram and interpret such reply and/orforward the reply to a management console interfaced to the chassismanagement controller.

As depicted in FIG. 1, a switch 110 may have coupled thereto one or moreslots 120. A slot 120 may include any system, device, or apparatusconfigured to allow addition of one or more expansion cards to chassis101 in order to electrically coupled such expansion cards to a switch110. Such slots 120 may comprise any suitable combination of full-heightrisers, full-height slots, and low-profile slots. A full-height risermay include any system, device, or apparatus configured to allowaddition of one or more expansion cards (e.g., a full-height slot)having a physical profile or form factor with dimensions thatpractically prevent such expansion cards to be coupled in a particularmanner (e.g., perpendicularly) to mid-plane 106 and/or switch 110 (e.g.,the proximity of information handling resources in chassis 101 preventsphysical placement of an expansion card in such manner). Accordingly, afull-height riser may itself physically couple with a low-profile tomid-plane 106, a switch 110, or another components, and full-heightcards may then be coupled to full-height slots of full-height riser. Onthe other hand, low-profile slots may be configured to couplelow-profile expansion cards to switches 110 without the need for afull-height riser.

Slots 120 may also include electrically conductive elements (e.g., edgeconnectors, traces, etc.) allowing for expansion cards inserted intoslots 120 to be electrically coupled to switches 110. In operation,switches 110 may manage switching of communications between individualinformation handling systems 102 and expansion cards coupled to slots120. In some embodiments, slots 120 may be nonshared (e.g., each slot120 is associated with a single information handling system 102). Inother embodiments, one or more of slots 120 may be shared among two ormore information handling systems 102. In these and other embodiments,one or more slots 120 may be configured to be compatible with PCIe,generalized PC bus switch, Infiniband, or other suitable communicationspecification, standard, or protocol.

Network interface 116 may include any suitable system, apparatus, ordevice operable to serve as an interface between chassis 101 and anexternal network (e.g., a local area network or other network). Networkinterface 116 may enable information handling systems 102 to communicatewith the external network using any suitable transmission protocol(e.g., TCP/IP) and/or standard (e.g., IEEE 802.11, Wi-Fi). In certainembodiments, network interface 116 may include a network interface card(NIC). In the same or alternative embodiments, network interface 116 maybe configured to communicate via wireless transmissions. In the same oralternative embodiments, network interface 116 may provide physicalaccess to a networking medium and/or provide a low-level addressingsystem (e.g., through the use of Media Access Control addresses). Insome embodiments, network interface 116 may be implemented as a localarea network (LAN) on motherboard (LOM) interface.

In some embodiments, various components of chassis 101 may be coupled toa planar. For example, a planar may interconnect switches 110, chassismanagement controller 112, storage controllers 114, network interface116, optical media drive 132, KVM interface 134, user interface 136,and/or other modular information handling resources of chassis 101 tomid-plane 106 of system 100. Accordingly, such planar may include slotsand/or connectors configured to interconnect with such informationhandling resources.

Storage interfaces 126 may include any system, device, or apparatusconfigured to facilitate communication between storage controllers 114and disk drives 130. For example, a storage interface may serve topermit a relatively small number of communication links (e.g., two)between storage controllers 114 and storage interfaces 126 tocommunicate with a greater number of disk drives 130. Thus, a storageinterface 126 may provide a switching mechanism and/or disk driveaddressing mechanism that allows an information handling system 102 tocommunicate with numerous disk drives 130 via a limited number ofcommunication links and/or channels. Accordingly, a storage interface126 may operate like an Ethernet hub or network switch that allowsmultiple systems to be coupled using a single switch port (or relativelyfew switch ports). A storage interface 126 may be implemented as anexpander (e.g., a Serial Attached SCSI (SAS) expander), an Ethernetswitch, a FibreChannel switch, Internet Small Computer System Interface(iSCSI) switch, or any other suitable switch. In order to support highavailability storage, system 100 may implement a plurality of redundantstorage interfaces 126, as shown in FIG. 1.

Disk drive backplane 128 may comprise any system, device, or apparatusconfigured to interconnect modular storage interfaces 126 with modulardisk drives 130. Accordingly, disk drive backplane 128 may include slotsand/or connectors configured to receive storage interfaces 126 and/ordisk drives 130. In some embodiments, system 100 may include two or morebackplanes, in order to support differently-sized disk drive formfactors. To support redundancy and high availability, a backplane 128may be configured to receive a plurality (e.g., 2) of storage interfaces126 which couple two storage controllers 114 to each disk drive 130.

Each disk drive 130 may include computer-readable media (e.g., magneticstorage media, optical storage media, opto-magnetic storage media,and/or other type of rotating storage media, flash memory, and/or othertype of solid state storage media) and may be generally operable tostore data and/or programs (e.g., one or more operating systems and/orone or more application programs). Although disk drives 130 are depictedas being internal to chassis 101 in FIG. 1, in some embodiments, one ormore disk drives may be located external to chassis 101 (e.g., in one ormore enclosures external to chassis 101).

Optical media drive 132 may be coupled to mid-plane 106 and may includeany suitable system, apparatus, or device configured to read data fromand/or write data to an optical storage medium (e.g., a compact disc(CD), digital versatile disc (DVD), blue laser medium, and/or otheroptical medium). In certain embodiments, optical media drive 132 may uselaser light or other electromagnetic energy to read and/or write data toan optical storage medium. In some embodiments, optical media drive 132may be nonshared and may be user-configurable such that optical mediadrive 132 is associated with a single information handling system 102.

KVM interface 134 may be coupled to mid-plane 106 and may include anysuitable system, apparatus, or device configured to couple to one ormore of a keyboard, video display, and mouse and act as switch betweenmultiple information handling systems 102 and the keyboard, videodisplay, and/or mouse, thus allowing a user to interface with aplurality of information handling systems 102 via a single keyboard,video display, and/or mouse.

User interface 136 may include any system, apparatus, or device viawhich a user may interact with system 100 and its various informationhandling resources by facilitating input from a user allowing the userto manipulate system 100 and output to a user allowing system 100 toindicate effects of the user's manipulation. For example, user interface136 may include a display suitable for creating graphic images and/oralphanumeric characters recognizable to a user, and may include, forexample, a liquid crystal display (LCD), cathode ray tube (CRT), aplasma screen, and/or a digital light processor (DLP) projectionmonitor. In certain embodiments, such a display may be an integral partof chassis 101 and receive power from power supplies (not explicitlyshown) of chassis 101, rather than being coupled to chassis 101 via acable. In some embodiments, such display may comprise a touch screendevice capable of receiving user input, wherein a touch sensor may bemechanically coupled or overlaid upon the display and may comprise anysystem, apparatus, or device suitable for detecting the presence and/orlocation of a tactile touch, including, for example, a resistive sensor,capacitive sensor, surface acoustic wave sensor, projected capacitancesensor, infrared sensor, strain gauge sensor, optical imaging sensor,dispersive signal technology sensor, and/or acoustic pulse recognitionsensor. In these and other embodiments, user interface 136 may includeother user interface elements (e.g., a keypad, buttons, and/or switchesplaced in proximity to a display) allowing a user to provide input tosystem 100. User interface 136 may be coupled to chassis managementcontrollers 112 and/or other components of system 100, and thus mayallow a user to configure various information handling resources ofsystem 100 (e.g., assign individual information handling systems 102 toparticular information handling resources).

FIG. 2 illustrates a flow chart of an example method for virtualizationof storage services in an integrated chassis, in accordance with certainembodiments of the present disclosure. According to certain embodiments,method 200 may begin at step 202. As noted above, teachings of thepresent disclosure may be implemented in a variety of configurations ofsystem 100. As such, the preferred initialization point for method 200and the order of the steps 202-220 comprising method 200 may depend onthe implementation chosen.

At step 202, a chassis management controller (e.g., a chassis managementcontroller 112) may receive a storage management command (e.g., astorage application programming interface (API) call) from a managementconsole or other interface communicatively coupled to the chassismanagement controller and encapsulate the storage management command ina datagram (e.g., an Ethernet packet, frame, or other datagram).

At step 204, the chassis management controller may communicate thedatagram to a switch management controller (e.g., switch managementcontroller 111). Such communication may be made over a private networkof a chassis housing both of the chassis management controller and theswitch management controller. In some embodiments, such communicationmay be made using TCP/IP.

At step 206, the switch management controller may extract (e.g.,decapsulate) the storage management command from the datagram. At step208, based on analysis of the command, the storage management controllermay identify a storage controller (e.g., a storage controller 114)associated with the command. At step 210, the switch managementcontroller may communicate via an appropriate switch (e.g., a switch110) an input/output control request based on the storage managementcommand to the identified storage controller.

At step 212, the switch management controller may receive from theidentified storage controller via an appropriate switch a reply to theinput/output control request. At step 214, the switch managementcontroller may encapsulate the storage management command in a datagram(e.g., an Ethernet packet, frame, or other datagram). At step 216, theswitch management controller may communicate the datagram to the chassismanagement controller. Such communication may be made over a privatenetwork of a chassis housing both of the chassis management controllerand the switch management controller. In some embodiments, suchcommunication may be made using TCP/IP.

At step 218, the chassis management controller may extract (e.g.,decapsulate) the reply from the datagram. At step 220, the chassismanagement controller may communicate the reply to the sender (e.g., amanagement console) of the storage management controller. Aftercompletion of step 220, method 200 may end.

The storage controller 114 may communicate a reply (e.g., a return code)to storage management controller 111, which reply storage managementcontroller 111 may encapsulate into a network datagram (e.g., anEthernet packet, frame, or other datagram) and communicate such datagramvia the private network to a chassis management controller 112. Thechassis management controller 112 may extract the reply from thedatagram and interpret such reply and/or forward the reply to amanagement console interfaced to the chassis management controller.

***

Although FIG. 2 discloses a particular number of steps to be taken withrespect to method 200, method 200 may be executed with greater or lessersteps than those depicted in FIG. 2. In addition, although FIG. 2discloses a certain order of steps to be taken with respect to method200, the steps comprising method 200 may be completed in any suitableorder.

Method 200 may be implemented using system 100, components thereof orany other system operable to implement method 200. In certainembodiments, method 200 may be implemented partially or fully insoftware and/or firmware embodied in computer-readable media.

Although the present disclosure has been described in detail, it shouldbe understood that various changes, substitutions, and alterations canbe made hereto without departing from the spirit and the scope of thedisclosure as defined by the appended claims.

What is claimed is:
 1. A system comprising: a chassis configured toreceive a plurality of modular information handling systems; one or morechassis management controllers housed in the chassis and configured to:receive a storage management command; encapsulate the storage managementcommand in a first datagram; and communicate the first datagram to aswitch management controller housed in the chassis; and the switchmanagement controller configured to: extract the storage managementcommand from the first datagram; identify a storage controllerassociated with the storage management command; and communicate aninput/output control request to the storage controller based on thestorage management command.
 2. A system according to claim 1, thecommand originating from a management console communicatively coupled tothe one or more chassis management controllers.
 3. A system according toclaim 1, the datagram comprising an Ethernet frame.
 4. A systemaccording to claim 1, the one or more chassis management controllersconfigured to communicate the first datagram to the switch managementcontroller via Transmission Control Protocol/Internet Protocol.
 5. Asystem according to claim 1, the one or more chassis managementcontrollers configured to communicate the first datagram to the switchmanagement controller via a private network internal to the chassis. 6.A system according to claim 1, the switch management controllerconfigured to communicate the input/output control request to thestorage controller via a switch.
 7. A system according to claim 6, theswitch compliant with Peripheral Component Interconnect Express.
 8. Asystem according to claim 1, the switch management controller furtherconfigured to: receive a reply to the input/output control request fromthe storage controller; encapsulate the reply in a second datagram; andcommunicate the second datagram to the one or more chassis managementcontrollers.
 9. A system according to claim 8, the chassis managementcontroller further configured to: extract the reply from the seconddatagram; and communicate the reply to an originator of the storagemanagement command.
 10. A system according to claim 1, the chassismanagement controller further configured to: receive a second datagramhaving encapsulated therein a reply to the input/output control request;extract the reply from the second datagram; and communicate the reply toan originator of the storage management command.
 11. A methodcomprising: receiving a storage management command at a chassismanagement controller housed in a chassis configured to receive aplurality of modular information handling systems; encapsulating thestorage management command in a first datagram; communicating the firstdatagram from the chassis management controller to a switch managementcontroller housed in the chassis; extracting the storage managementcommand from the first datagram; identifying a storage controllerassociated with the storage management command; and communicating aninput/output control request from the switch management controller tothe storage controller based on the storage management command.
 12. Amethod according to claim 11, the command originating from a managementconsole communicatively coupled to the chassis management controller.13. A method according to claim 11, the datagram comprising an Ethernetframe.
 14. A method according to claim 11, wherein communicating thefirst datagram comprises communicating the first datagram viaTransmission Control Protocol/Internet Protocol.
 15. A method accordingto claim 11, wherein communicating the first datagram comprisescommunicating the first datagram via a private network internal to thechassis.
 16. A method according to claim 11, wherein communicating theinput/output control request comprises communicating the input/outputcontrol request to the storage controller via a switch.
 17. A methodaccording to claim 16, the switch compliant with Peripheral ComponentInterconnect Express.
 18. A method according to claim 11, furthercomprising: receiving a reply to the input/output control request fromthe storage controller; encapsulating the reply in a second datagram;and communicating the second datagram from the switch managementcontroller to the chassis management controller.
 19. A method accordingto claim 18, further comprising: extracting the reply from the seconddatagram; and communicating the reply to an originator of the storagemanagement command.
 20. A method according to claim 11, furthercomprising: receiving at the chassis management controller a seconddatagram having encapsulated therein a reply to the input/output controlrequest; extracting the reply from the second datagram; andcommunicating the reply to an originator of the storage managementcommand.